American Express redesigned their payment platform using cell-based architecture—independent, self-contained processing units that isolate failures and keep transactions moving even when parts of the system fail. The system routes transactions deterministically to cells holding the right data, avoiding cross-cell dependencies during payment processing.

• Cells are failure boundaries, not functional units: each cell contains everything needed to process a transaction (microservices, databases, DNS) so problems stay contained and don't cascade across the platform.
• Data strategy varies by change frequency: immutable and semi-static data gets pushed to all cells before transactions arrive, while dynamic data triggers deterministic routing to send transactions to cells holding current state.
• The Global Transaction Router enforces cell isolation by being the only path between cells and external systems, kept deliberately simple to avoid becoming a bottleneck—it just parses messages and routes, leaving all business logic to the cells.

This Dev newsletter covers American Express’s cell-based payment system for high availability, a persistent agent memory layer on Elasticsearch, and a large-scale malware campaign on GitHub. It also highlights AI agent security roadmaps, GDPR consent fines, compiler reproducibility fixes, and new autonomous agent frameworks.

• A team built persistent agent memory by layering episodic/semantic/procedural Elasticsearch indices, hitting 0.89 recall with zero cross-tenant leaks
• Attackers flooded GitHub with 10,000 malicious repos hiding Trojans in ZIPs, constantly swapping readme links and commits to outpace detection
• Norway's DPA fined Elkjop €1.8 million for illegally forcing marketing consent as a condition of customer sign-up, a clear GDPR violation
• American Express uses a cell-based architecture where independent processing "cells" isolate failures so one crash doesn't cascade across the payments system

American Express uses a cell-based architecture to isolate failures and maintain low-latency, predictable performance in its core payments platform. Each cell contains its own microservices and data, while a Global Transaction Router directs transactions to the cell with the required state. Asynchronous replication and strict ingress/egress boundaries keep cells independent and limit failure blast radius.

• Amex isolates payment processing into self-sufficient cells so failures stay contained and don't ripple across the whole system.
• Static reference data (currency rates, merchant codes) is pre-pushed to every cell, avoiding fallback lookups that would slow transactions.
• A Global Transaction Router directs each transaction to the cell holding authoritative state, with async replication kept outside the critical path to avoid latency.
• All inter-cell communication is forced through the router/payment mesh, enforcing strict boundaries so transactions can't bypass a failing cell.